Intelligent long term evolution peer-to-peer management

ABSTRACT

A device may receive a peer-to-peer communication, receive a capability of a second device associated with the peer-to-peer communication, and provide instructions to adjust a peer-to-peer communication based on the capability of the device.

TECHNICAL FIELD

The technical field generally relates to wireless communications andmore specifically relates to peer-to-peer communications.

BACKGROUND

Peer-to-peer (P2P) networks can be set up in the home, in a business, orover the Internet. Each network type can require all computers in thenetwork to use the same or a compatible program to connect to each otherand access files and other resources found on the other computer. P2Pnetworks can be used for sharing content such as audio, video, data oranything in digital format.

P2P is a distributed application architecture that partitions tasks orworkloads among peers. Peers can be equally privileged participants inthe application. The owner of each computer on a P2P network may setaside a portion of its resources such as processing power, disk storageor network bandwidth to be made directly available to other networkparticipants.

SUMMARY

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used to limit the scope of the claimed subject matter. Furthermore,the claimed subject matter is not limited to limitations that solve anyor all disadvantages noted in any part of this disclosure.

Systems, methods, and devices are disclosed for peer-to-peercommunications. In an embodiment, first device may receive apeer-to-peer (P2P) communication, receive a capability of a seconddevice associated with the peer-to-peer communication, and provideinstructions to adjust a characteristic of the P2P communication basedon the capability of the device.

BRIEF DESCRIPTION OF THE DRAWINGS

The following detailed description is better understood when read inconjunction with the appended drawings. For the purposes ofillustration, there is shown in the drawings exemplary embodiments;however, the subject matter is not limited to the specific elements andinstrumentalities disclosed. In the drawings:

FIG. 1 illustrates a non-limiting exemplary network configuration forimplementing one or more disclosed embodiments.

FIG. 2 illustrates a non-limiting exemplary method of implementing oneor more disclosed embodiments.

FIG. 3 is a block diagram of a non-limiting exemplary mobile device inwhich aspects of one or more disclosed embodiments may be implemented.

FIG. 4 is a block diagram of a non-limiting exemplary processor in whichaspects of one or more disclosed embodiments may be implemented.

FIG. 5 is a block diagram of a non-limiting exemplary packet-basedmobile cellular network environment, such as a GPRS network, in whichone or more disclosed embodiments may be implemented.

FIG. 6 illustrates a non-limiting exemplary architecture of a typicalGPRS network, segmented into four groups, in which one or more disclosedembodiments may be implemented.

FIG. 7 illustrates a non-limiting alternate block diagram of anexemplary GSM/GPRS/IP multimedia network architecture in which one ormore disclosed embodiments may be implemented.

FIG. 8 illustrates a PLMN block diagram view of an exemplaryarchitecture in which one or more disclosed embodiments may beimplemented.

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

FIG. 1 is an exemplary illustration of a communications system 100 inwhich one or more of the disclosed embodiments may be implemented. InFIG. 1, a wireless transmit/receive unit (WTRU) 105 may connect to aneNode B 102 and a WTRU 110 may connect to an eNode B 106. The eNode B102 and eNode B 104 may connect to a core network 104. Connected to corenetwork 104 may be the Internet 112, other Networks 114 which mayinclude a packet switched telephone network. The core network maycomprise or be connected to a peer-to-peer (abbreviated herein as P2P)core network device 108. Network device 108 may be involved with a P2Psession and may be located anywhere within communication system 100.

FIG. 2 illustrates method 200 of intelligent peer-to-peer management.Note that the functions and/or actions described in regard to any of theblocks of method 200 or other method discussed herein may be performedin any order, in isolation, with a subset of other functions and/oractions described in regard to any of the other blocks of method 200,and in combination with other functions and/or actions, including thosedescribed herein and those not set forth herein. All such embodimentsare contemplated as within the scope of the present disclosure.

At block 210 of method 200, a mobile device (e.g., a WTRU) may initiatea P2P session. A WTRU may include user equipment (UE), a mobile station,a mobile device, a fixed or mobile subscriber unit, a pager, a cellulartelephone, a personal digital assistant (PDA), a smartphone, a laptop, anetbook, a personal computer, a wireless sensor, consumer electronics,and the like. At block 220, a P2P core network device or other networkdevice may intercept the initiated P2P session. The core network may beconfigured to route the initiated P2P session to the P2P core networkdevice after determining that the packet is P2P traffic. Thedetermination of P2P traffic may occur by the use of packet inspection.In an embodiment, the mobile device may be configured with an IP addressor other appropriate address of the P2P core network device and may beconfigured to send initial requests for a P2P session with any networkdevice to the P2P core network device.

In an embodiment, the core network may direct all P2P session trafficthrough the P2P core network device and the redirection may be invisibleto the mobile devices that are involved with the P2P session. Forexample, the core network may route the traffic by inspecting allpackets entering the network and route the P2P packets through the P2Pcore network device. Alternatively, the core network may be configuredto inspect and direct the packets of mobile devices that are capable ofdoing P2P communication. In another example, the core network may beconfigured to inspect and direct the packets of all mobile devices thathave registered to do P2P.

At block 230 of method 200, the P2P core network device may determinethe peer-to-peer capability of the initiating P2P session mobile deviceas well as all other devices that may desire to participate in the P2Psession. The P2P core network device may be aware of the capability ofP2P session devices through various ways. For example, the P2P corenetwork device may request the device capability of each device thatdesires a P2P session. Alternatively, each device that desires a P2Psession may be configured to send device capability information sometimebefore or during a P2P session. In another example, device capabilityinformation may periodically be updated and housed on a core networkdevice. The P2P core network device may query the core network devicefor device capability. Lastly, some combination or fallback of theexamples disclosed herein may be used to determine the device capabilityfor each device that desires a P2P session. For example, a database maybe queried first and if the database is unavailable or the device is notfound in the database then the device may be queried. Capability, asdiscussed herein, may include a device's software and accompanyingfeatures, hardware (e.g., processor speed, display screen, or amount ofread only memory), upload and download speeds, and the like.

The P2P core network device, at block 240, may adjust the P2P sessionbased on the device capability of the involved P2P session devices.Sessions may be adjusted in order to perform content adaptation betweendevices when capability mismatches occur. For example, an “old”smartphone user may desire to play a game with a “new” tablet computeruser. The old smartphone may not have the updated software and hardwarecapabilities of the new tablet user. Here, the P2P core network devicemay intercede and adjust the characteristics of a P2P communication(e.g., graphics options, sound options, or other features) in a mannerin which the old smartphone and the new tablet can communicate withouthaving to upgrade or downgrade software or hardware on the smartphone ortablet device. More specifically, in an embodiment a P2P core networkdevice may translate the P2P packet of the new tablet into a new P2Ppacket that may be interpreted with little or no issue by the oldsmartphone. Again, this may allow for options such as sound and graphicsto be removed or interpreted in a manner that is easily or optimallyinterpreted by a destination P2P device. In another example, a P2Pcommunication may be adjusted by a P2P core network device to allow fora destination P2P device so the processor use may be optimized for otherapplications. In this latter example, the destination P2P device may beable to interpret the “original” P2P communication, but it may not beoptimal for the destination P2P device.

In an embodiment, a P2P core network device may adjust some P2P sessionsbased on device capability and direct other P2P session devices toadjust their P2P communication. For example, the old smartphone may notbe compatible (or optimally communicate) with the new tablet. Yet, thetablet may have the capability of adjusting its P2P communication to beoptimal or compatible with the old smartphone. The P2P core networkdevice, which may already have the device capabilities on file, maydirect the tablet to adjust its settings for optimal or compatiblecommunication. The P2P core network device may take no further activerole in P2P session and the smartphone and tablet may continue tocommunicate directly. This may allow for faster setup and P2Pcommunication with devices of different capabilities, especially if theP2P core network device is located at a connecting base station of a P2Psession device.

In an embodiment, the P2P core network device may adjust P2P sessionbased further on a user profile or a network service provider's definedconditions. For example, the camera capability may be turned off by theP2P core network device when a P2P session device is at a particularlocation. The location may be determined by a global positioning system,proximity to a base station, and the like. In general, the P2P corenetwork device may be able to disable device capability during end userdefined or network provider defined conditions.

In an embodiment, the P2P core network device may only intercept theinitial P2P session inquiry. If the devices are compatible or there areno other restrictions the P2P core network device may be configured toforward packets indefinitely without further P2P related packetinspection, forward packets with P2P related packet inspection atperiodic time intervals (e.g., every 30 minutes), or the like. Inaddition, the P2P core network device may direct core network devices torefrain from P2P related packet inspection or routing to the P2P corenetwork device for a period of time.

FIG. 3 illustrates an example wireless device 1010 that may be used inconnection with an embodiment. References will also be made to otherfigures of the present disclosure as appropriate. For example, mobiledevices 105 and 110 may be wireless devices of the type described inregard to FIG. 3, and may have some, all, or none of the components andmodules described in regard to FIG. 3. It will be appreciated that thecomponents and modules of wireless device 1010 illustrated in FIG. 3 areillustrative, and that any number and type of components and/or modulesmay be present in wireless device 1010. In addition, the functionsperformed by any or all of the components and modules illustrated inFIG. 3 may be performed by any number of physical components. Thus, itis possible that in some embodiments the functionality of more than onecomponent and/or module illustrated in FIG. 3 may be performed by anynumber or types of hardware and/or software.

Processor 1021 may be any type of circuitry that performs operations onbehalf of wireless device 1010. Such circuitry may include circuitry andother components that enable processor 1021 to perform any of thefunctions and methods described herein. Such circuitry and othercomponents may also enable processor 1021 to communicate and/or interactwith other devices and components, for example any other component ofdevice of wireless device 1010, in such a manner as to enable processor118 and such other devices and/or components to perform any of thedisclosed functions and methods. In one embodiment, processor 1021executes software (i.e., computer readable instructions stored in acomputer readable medium) that may include functionality related tointelligent peer-to-peer management, for example. User interface module1022 may be any type or combination of hardware and/or software thatenables a user to operate and interact with wireless device 1010, and,in one embodiment, to interact with a system or software enabling theuser to place, request, and/or receive calls, text communications of anytype, voicemail, voicemail notifications, voicemail content and/or data,and/or a system or software enabling the user to view, modify, or deleterelated software objects. For example, user interface module 1022 mayinclude a display, physical and/or “soft” keys, voice recognitionsoftware, a microphone, a speaker and the like. Wireless communicationmodule 1023 may be any type of transmitter, receiver, or transceiverincluding hardware or a combination of hardware and/software thatenables wireless device 1010 to communicate with wireless networkequipment. Memory 1024 enables wireless device 1010 to storeinformation, such as APNs, MNCs, MCCs, text communications content andassociated data, multimedia content, software to efficiently processradio resource requests and service requests, and radio resource requestprocessing preferences and configurations. Memory 1024 may take anyform, such as internal random access memory (RAM), an SD card, a microSDcard and the like. Power supply 1025 may be a battery or other type ofpower input (e.g., a charging cable that is connected to an electricaloutlet, etc.) that is capable of powering wireless device 1010. SIM 1026may be any type Subscriber Identity Module and may be configured on aremovable or non-removable SIM card that allows wireless device 1010 tostore data on SIM 1026.

FIG. 4 is a block diagram of an example processor 1158 which may beemployed in any of the embodiments described herein, including as one ormore components of mobile devices 105 and 110, as one or more componentsof network equipment such as MMEs, and HSSs, and/or CMS, or any othercomponent of networks 210, 212, 216, and/or any related equipment,and/or as one or more components of any third party system or subsystemthat may implement any portion of the subject matter described herein.It is emphasized that the block diagram depicted in FIG. 4 is exemplaryand not intended to imply a specific implementation. Thus, the processor1158 can be implemented in a single processor or multiple processors.Multiple processors can be distributed or centrally located. Multipleprocessors can communicate wirelessly, via hard wire, or a combinationthereof. Processor 1158 may include circuitry and other components thatenable processor 1158 to perform any of the functions and methodsdescribed herein. Such circuitry and other components may also enableprocessor 1158 to communicate and/or interact with other devices andcomponents, for example any other component of any device disclosedherein or any other device, in such a manner as to enable processor 1158and such other devices and/or components to perform any of the disclosedfunctions and methods.

As depicted in FIG. 4, the processor 1158 comprises a processing portion1160, a memory portion 1162, and an input/output portion 1164. Theprocessing portion 1160, memory portion 1162, and input/output portion1164 are coupled together (coupling not shown in FIG. 4) to allowcommunications between these portions. The input/output portion 1164 iscapable of providing and/or receiving components, commands, and/orinstructions, utilized to, for example, request and receive APNs, MNCs,and/or MCCs, establish and terminate communications sessions, transmitand receive service requests and data access request data and responses,transmit, receive, store and process text, data, and voicecommunications, execute software that efficiently processes radioresource requests, receive and store service requests and radio resourcerequests, radio resource request processing preferences andconfigurations, and/or perform any other function described herein.

The processor 1158 may be implemented as a client processor and/or aserver processor. In a basic configuration, the processor 1158 mayinclude at least one processing portion 1160 and memory portion 1162.The memory portion 1162 can store any information utilized inconjunction with establishing, transmitting, receiving, and/orprocessing text, data, and/or voice communications,communications-related data and/or content, voice calls, othertelephonic communications, etc. For example, the memory portion iscapable of storing APNs, MNCs, MCCs, service requests, radio resourcerequests, QoS and/or APN parameters, software for intelligent peer-topeer communications, text and data communications, calls, voicemail,multimedia content, visual voicemail applications, etc. Depending uponthe exact configuration and type of processor, the memory portion 1162can be volatile (such as RAM) 1166, non-volatile (such as ROM, flashmemory, etc.) 1168, or a combination thereof. The processor 1158 canhave additional features/functionality. For example, the processor 1158may include additional storage (removable storage 1170 and/ornon-removable storage 1172) including, but not limited to, magnetic oroptical disks, tape, flash, smart cards or a combination thereof.Computer storage media, such as memory and storage elements 1162, 1170,1172, 1166, and 1168, may include volatile and nonvolatile, removableand non-removable media implemented in any method or technology forstorage of information such as computer readable instructions, datastructures, program modules, or other data. Computer storage mediainclude, but are not limited to, RAM, ROM, EEPROM, flash memory or othermemory technology, CD-ROM, digital versatile disks (DVD) or otheroptical storage, magnetic cassettes, magnetic tape, magnetic diskstorage or other magnetic storage devices, universal serial bus (USB)compatible memory, smart cards, or any other medium that can be used tostore the desired information and that can be accessed by the processor1158. Any such computer storage media may be part of the processor 1158.It is to be understood that a computer storage medium, as describedherein, is not to be construed as a transient signal.

The processor 1158 may also contain the communications connection(s)1180 that allow the processor 1158 to communicate with other devices,for example through a radio access network (RAN). Communicationsconnection(s) 1180 is an example of communication media. Communicationmedia typically embody computer-readable instructions, data structures,program modules or other data in a modulated data signal such as acarrier wave or other transport mechanism and includes any informationdelivery media. The term “modulated data signal” means a signal that hasone or more of its characteristics set or changed in such a manner as toencode information in the signal. By way of example, and not limitation,communication media includes wired media such as a wired network ordirect-wired connection as might be used with a land line telephone, andwireless media such as acoustic, RF, infrared, cellular, and otherwireless media. The term computer-readable media as used herein includesboth storage media and communication media. It is to be understood,however, that a computer-readable storage medium, as described herein,is not to be construed as a transient signal. The processor 1158 alsocan have input device(s) 1176 such as keyboard, keypad, mouse, pen,voice input device, touch input device, etc. Output device(s) 1174 suchas a display, speakers, printer, etc. also can be included.

A RAN as described herein may comprise any telephony radio network, orany other type of communications network, wireline or wireless, or anycombination thereof. The following description sets forth some exemplarytelephony radio networks, such as the global system for mobilecommunications (GSM), and non-limiting operating environments. Thebelow-described operating environments should be considerednon-exhaustive, however, and thus the below-described networkarchitectures merely show how intelligent peer-to-peer management may beimplemented with stationary and non-stationary network structures andarchitectures in order to do intelligent peer-to-peer management. It canbe appreciated, however, that intelligent peer-to-peer management asdescribed herein may be incorporated with existing and/or futurealternative architectures for communication networks as well.

The GSM is one of the most widely utilized wireless access systems intoday's fast growing communication environment. The GSM providescircuit-switched data services to subscribers, such as mobile telephoneor computer users. The General Packet Radio Service (GPRS), which is anextension to GSM technology, introduces packet switching to GSMnetworks. The GPRS uses a packet-based wireless communication technologyto transfer high and low speed data and signaling in an efficientmanner. The GPRS attempts to optimize the use of network and radioresources, thus enabling the cost effective and efficient use of GSMnetwork resources for packet mode applications.

The exemplary GSM/GPRS environment and services described herein alsomay be extended to 3G services, such as Universal Mobile TelephoneSystem (UMTS), Frequency Division Duplexing (FDD) and Time DivisionDuplexing (TDD), High Speed Packet Data Access (HSPDA), cdma2000 1×Evolution Data Optimized (EVDO), Code Division Multiple Access-2000(cdma2000 3×), Time Division Synchronous Code Division Multiple Access(TD-SCDMA), Wideband Code Division Multiple Access (WCDMA), EnhancedData GSM Environment (EDGE), International MobileTelecommunications-2000 (IMT-2000), Digital Enhanced CordlessTelecommunications (DECT), 4G Services such as Long Term Evolution(LTE), etc., as well as to other network services that become availablein time. In this regard, intelligent peer-to-peer management may beapplied independently of the method of data transport.

Embodiments disclosed herein may allow for communications single andnetwork service provider networks. P2P notification messages may be sentacross the network(s) from a P2P end device to another P2P end device toquery communication availability of a P2P end device. Communicationavailability may include uptime, bandwidth resources of for uplink anddownlink communication, and the like.

FIG. 5 depicts an overall block diagram of an exemplary packet-basedmobile cellular network environment, such as a GPRS network, in whichintelligent peer-to-peer management systems and methods such as thosedescribed herein may be practiced. In an example configuration, any RANas described herein may be encompassed by or interact with the networkenvironment depicted in FIG. 5. Similarly, mobile devices 105 and 110may communicate or interact with a network environment such as thatdepicted in FIG. 5. In such an environment, there may be a plurality ofBase Station Subsystems (BSS) 900 (only one is shown), each of whichcomprises a Base Station Controller (BSC) 902 serving a plurality ofBase Transceiver Stations (BTS) such as BTSs 904, 906, and 908. BTSs904, 906, 908, etc. are the access points where users of packet-basedmobile devices (e.g., mobile devices 210, 310, and 610) become connectedto the wireless network. In exemplary fashion, the packet trafficoriginating from user devices (e.g., mobile devices 105 and 110) may betransported via an over-the-air interface to a BTS 908, and from the BTS908 to the BSC 902. Base station subsystems, such as BSS 900, may be apart of internal frame relay network 910 that can include Service GPRSSupport Nodes (SGSN) such as SGSN 912 and 914. Each SGSN may beconnected to an internal packet network 920 through which a SGSN 912,914, etc. may route data packets to and from a plurality of gateway GPRSsupport nodes (GGSN) 922, 924, 926, etc. As illustrated, SGSN 914 andGGSNs 922, 924, and 926 may be part of internal packet network 920.Gateway GPRS serving nodes 922, 924 and 926 may provide an interface toexternal Internet Protocol (IP) networks, such as Public Land MobileNetwork (PLMN) 950, corporate intranets 940, or Fixed-End System (FES)or the public Internet 930. As illustrated, subscriber corporate network940 may be connected to GGSN 924 via firewall 932, and PLMN 950 may beconnected to GGSN 924 via border gateway router 934. The RemoteAuthentication Dial-In User Service (RADIUS) server 942 may be used forcaller authentication when a user of a mobile cellular device callscorporate network 940.

Generally, there can be four different cell sizes in a GSM network,referred to as macro, micro, pico, and umbrella cells. The coverage areaof each cell is different in different environments. Macro cells may beregarded as cells in which the base station antenna is installed in amast or a building above average roof top level. Micro cells are cellswhose antenna height is under average roof top level. Micro-cells may betypically used in urban areas. Pico cells are small cells having adiameter of a few dozen meters. Pico cells may be used mainly indoors.On the other hand, umbrella cells may be used to cover shadowed regionsof smaller cells and fill in gaps in coverage between those cells.

FIG. 6 illustrates an architecture of a typical GPRS network segmentedinto four groups: users 1050, radio access network 1060, core network1070, and interconnect network 1080. Users 1050 may comprise a pluralityof end users (though only mobile subscriber 1055 is shown in FIG. 6). Inan example embodiment, the device depicted as mobile subscriber 1055 maycomprise any of mobile devices 105 and 110. Radio access network 1060comprises a plurality of base station subsystems such as BSSs 1062,which include BTSs 1064 and BSCs 1066. Core network 1070 comprises ahost of various network elements. As illustrated here, core network 1070may comprise Mobile Switching Center (MSC) 1071, Service Control Point(SCP) 1072, gateway MSC 1073, SGSN 1076, Home Location Register (HLR)1074, Authentication Center (AuC) 1075, Domain Name Server (DNS) 1077,and GGSN 1078. Interconnect network 1080 may also comprise a host ofvarious networks and other network elements. As illustrated in FIG. 6,interconnect network 1080 comprises Public Switched Telephone Network(PSTN) 1082, Fixed-End System (FES) or Internet 1084, firewall 1088, andCorporate Network 1089.

A mobile switching center may be connected to a large number of basestation controllers. At MSC 1071, for instance, depending on the type oftraffic, the traffic may be separated in that voice may be sent toPublic Switched Telephone Network (PSTN) 1082 through Gateway MSC (GMSC)1073, and/or data may be sent to SGSN 1076 that may send the datatraffic to GGSN 1078 for further forwarding.

When MSC 1071 receives call traffic, for example, from BSC 1066, it maysend a query to a database hosted by SCP 1072. The SCP 1072 may processthe request and may issue a response to MSC 1071 so that it may continuecall processing as appropriate.

The HLR 1074 may be a centralized database for users to register to theGPRS network. In some embodiments, HLR 1074 may be a device such asHSSs. HLR 1074 may store static information about the subscribers suchas the International Mobile Subscriber Identity (IMSI), APN profiles asdescribed herein, subscribed services, and a key for authenticating thesubscriber. HLR 1074 may also store dynamic subscriber information suchas dynamic APN profiles and the current location of the mobilesubscriber. HLR 1074 may also serve to intercept and determine thevalidity of destination numbers in messages sent from a device, such asmobile subscriber 1055, as described herein. Associated with HLR 1074may be AuC 1075. AuC 1075 may be a database that contains the algorithmsfor authenticating subscribers and may include the associated keys forencryption to safeguard the user input for authentication.

In the following, depending on context, the term “mobile subscriber”sometimes refers to the end user and sometimes to the actual portabledevice, such as mobile devices 105 and 110, used by an end user of amobile cellular service or a wireless provider. When a mobile subscriberturns on his or her mobile device, the mobile device may go through anattach process by which the mobile device attaches to an SGSN of theGPRS network. In FIG. 6, when mobile subscriber 1055 initiates theattach process by turning on the network capabilities of the mobiledevice, an attach request may be sent by mobile subscriber 1055 to SGSN1076. The SGSN 1076 queries another SGSN, to which mobile subscriber1055 was attached before, for the identity of mobile subscriber 1055.Upon receiving the identity of mobile subscriber 1055 from the otherSGSN, SGSN 1076 may request more information from mobile subscriber1055. This information may be used to authenticate mobile subscriber1055 to SGSN 1076 by HLR 1074. Once verified, SGSN 1076 sends a locationupdate to HLR 1074 indicating the change of location to a new SGSN, inthis case SGSN 1076. HLR 1074 may notify the old SGSN, to which mobilesubscriber 1055 was attached before, to cancel the location process formobile subscriber 1055. HLR 1074 may then notify SGSN 1076 that thelocation update has been performed. At this time, SGSN 1076 sends anAttach Accept message to mobile subscriber 1055, which in turn sends anAttach Complete message to SGSN 1076.

After attaching itself to the network, mobile subscriber 1055 may thengo through the authentication process. In the authentication process,SGSN 1076 may send the authentication information to HLR 1074, which maysend information back to SGSN 1076 based on the user profile that waspart of the user's initial setup. The SGSN 1076 may then send a requestfor authentication and ciphering to mobile subscriber 1055. The mobilesubscriber 1055 may use an algorithm to send the user identification(ID) and password to SGSN 1076. The SGSN 1076 may use the same algorithmand compares the result. If a match occurs, SGSN 1076 authenticatesmobile subscriber 1055.

Next, the mobile subscriber 1055 may establish a user session with thedestination network, corporate network 1089, by going through a PacketData Protocol (PDP) activation process. Briefly, in the process, mobilesubscriber 1055 may request access to an Access Point Name (APN), forexample, UPS.com, and SGSN 1076 may receive the activation request frommobile subscriber 1055. SGSN 1076 may then initiate a Domain NameService (DNS) query to learn which GGSN node has access to the UPS.comAPN. The DNS query may be sent to the DNS server within the core network1070, such as DNS 1077, that may be provisioned to map to one or moreGGSN nodes in the core network 1070. Based on the APN, the mapped GGSN1078 may access the requested corporate network 1089. The SGSN 1076 maythen send to GGSN 1078 a Create Packet Data Protocol (PDP) ContextRequest message that contains necessary information. The GGSN 1078 maysend a Create PDP Context Response message to SGSN 1076, which may thensend an Activate PDP Context Accept message to mobile subscriber 1055.

Once activated, data packets of the call made by mobile subscriber 1055may then go through radio access network 1060, core network 1070, andinterconnect network 1080, in a particular fixed-end system, or Internet1084 and firewall 1088, to reach corporate network 1089.

Thus, network elements that can invoke the functionality of intelligentpeer-to-peer management systems and methods such as those describedherein may include, but are not limited to, Gateway GPRS Support Nodetables, Fixed End System router tables, firewall systems, VPN tunnels,and any number of other network elements as required by the particulardigital network.

FIG. 7 illustrates another exemplary block diagram view of a GSM/GPRS/IPmultimedia network architecture 1100 in which the systems and methodsfor intelligent peer-to-peer management such as those described hereinmay be incorporated. As illustrated, architecture 1100 of FIG. 7includes a GSM core network 1101, a GPRS network 1130 and an IPmultimedia network 1138. The GSM core network 1101 includes a MobileStation (MS) 1102, at least one Base Transceiver Station (BTS) 1104 anda Base Station Controller (BSC) 1106. The MS 1102 is physical equipmentor Mobile Equipment (ME), such as a mobile telephone or a laptopcomputer (e.g., mobile devices 105 and 110) that is used by mobilesubscribers, in one embodiment with a Subscriber identity Module (SIM).The SIM includes an International Mobile Subscriber Identity (IMSI),which is a unique identifier of a subscriber. The SIM may also includeAPNs. The BTS 1104 may be physical equipment, such as a radio tower,that enables a radio interface to communicate with the MS. Each BTS mayserve more than one MS. The BSC 1106 may manage radio resources,including the BTS. The BSC may be connected to several BTSs. The BSC andBTS components, in combination, are generally referred to as a basestation (BSS) or radio access network (RAN) 1103.

The GSM core network 1101 may also include a Mobile Switching Center(MSC) 1108, a Gateway Mobile Switching Center (GMSC) 1110, a HomeLocation Register (HLR) 1112, Visitor Location Register (VLR) 1114, anAuthentication Center (AuC) 1118, and an Equipment Identity Register(EIR) 1116. The MSC 1108 may perform a switching function for thenetwork. The MSC may also perform other functions, such as registration,authentication, location updating, handovers, and call routing. The GMSC1110 may provide a gateway between the GSM network and other networks,such as an Integrated Services Digital Network (ISDN) or Public SwitchedTelephone Networks (PSTNs) 1120. Thus, the GMSC 1110 providesinterworking functionality with external networks.

The HLR 1112 may be a database that may contain administrativeinformation regarding each subscriber registered in a corresponding GSMnetwork. Such information may include APNs and APN profiles. The HLR1112 may also contain the current location of each MS. The VLR 1114 maybe a database that contains selected administrative information from theHLR 1112. The VLR may contain information necessary for call control andprovision of subscribed services for each MS currently located in ageographical area controlled by the VLR. The HLR 1112 and the VLR 1114,together with the MSC 1108, may provide the call routing and roamingcapabilities of GSM. The AuC 1116 may provide the parameters needed forauthentication and encryption functions. Such parameters allowverification of a subscriber's identity. The EIR 1118 may storesecurity-sensitive information about the mobile equipment.

A Short Message Service Center (SMSC) 1109 allows one-to-one shortmessage service (SMS), or multimedia message service (MMS), messages tobe sent to/from the MS 1102. A Push Proxy Gateway (PPG) 1111 is used to“push” (i.e., send without a synchronous request) content to the MS1102. The PPG 1111 acts as a proxy between wired and wireless networksto facilitate pushing of data to the MS 1102. A Short Message Peer toPeer (SMPP) protocol router 1113 may be provided to convert SMS-basedSMPP messages to cell broadcast messages. SMPP is a protocol forexchanging SMS messages between SMS peer entities such as short messageservice centers. The SMPP protocol is often used to allow third parties,e.g., content suppliers such as news organizations, to submit bulkmessages.

To gain access to GSM services, such as voice, data, short messageservice (SMS), and multimedia message service (MMS), the MS may firstregister with the network to indicate its current location by performinga location update and IMSI attach procedure. MS 1102 may send a locationupdate including its current location information to the MSC/VLR, viaBTS 1104 and BSC 1106. The location information may then be sent to theMS's HLR. The HLR may be updated with the location information receivedfrom the MSC/VLR. The location update may also be performed when the MSmoves to a new location area. Typically, the location update may beperiodically performed to update the database as location updatingevents occur.

GPRS network 1130 may be logically implemented on the GSM core networkarchitecture by introducing two packet-switching network nodes, aserving GPRS support node (SGSN) 1132, a cell broadcast and a GatewayGPRS support node (GGSN) 1134. The SGSN 1132 may be at the samehierarchical level as the MSC 1108 in the GSM network. The SGSN maycontrol the connection between the GPRS network and the MS 1102. TheSGSN may also keep track of individual MS's locations and securityfunctions and access controls.

Cell Broadcast Center (CBC) 1133 may communicate cell broadcast messagesthat are typically delivered to multiple users in a specified area. CellBroadcast is one-to-many geographically focused service. It enablesmessages to be communicated to multiple mobile telephone customers whoare located within a given part of its network coverage area at the timethe message is broadcast.

GGSN 1134 may provide a gateway between the GPRS network and a publicpacket network (PDN) or other IP networks 1136. That is, the GGSN mayprovide interworking functionality with external networks, and set up alogical link to the MS through the SGSN. When packet-switched dataleaves the GPRS network, it may be transferred to an external TCP-IPnetwork 1136, such as an X.25 network or the Internet. In order toaccess GPRS services, the MS first attaches itself to the GPRS networkby performing an attach procedure. The MS then activates a packet dataprotocol (PDP) context, thus activating a packet communication sessionbetween the MS, the SGSN, and the GGSN.

In a GSM/GPRS network, GPRS services and GSM services may be used inparallel. The MS may operate in one three classes: class A, class B, andclass C. A class A MS may attach to the network for both GPRS servicesand GSM services simultaneously. A class A MS may also supportsimultaneous operation of GPRS services and GSM services. For example,class A mobiles may receive GSM voice/data/SMS calls and GPRS data callsat the same time.

A class B MS may attach to the network for both GPRS services and GSMservices simultaneously. However, a class B MS does not supportsimultaneous operation of the GPRS services and GSM services. That is, aclass B MS can only use one of the two services at a given time.

A class C MS can attach for only one of the GPRS services and GSMservices at a time. Simultaneous attachment and operation of GPRSservices and GSM services is not possible with a class C MS.

GPRS network 1130 may be designed to operate in three network operationmodes (NOM1, NOM2 and NOM3). A network operation mode of a GPRS networkmay be indicated by a parameter in system information messagestransmitted within a cell. The system information messages may direct anMS where to listen for paging messages and how to signal towards thenetwork. The network operation mode represents the capabilities of theGPRS network. In a NOM1 network, a MS may receive pages from a circuitswitched domain (voice call) when engaged in a data call. The MS maysuspend the data call or take both simultaneously, depending on theability of the MS. In a NOM2 network, a MS may not receive pages from acircuit switched domain when engaged in a data call, since the MS may bereceiving data and may not be listening to a paging channel. In a NOM3network, a MS may monitor pages for a circuit switched network whilereceiving data and vice versa.

The IP multimedia network 1138 was introduced with 3GPP Release 5, andmay include IP multimedia subsystem (IMS) 1140 to provide richmultimedia services to end users. A representative set of the networkentities within IMS 1140 are a call/session control function (CSCF), amedia gateway control function (MGCF) 1146, a media gateway (MGW) 1148,and a master subscriber database, called a home subscriber server (HSS)1150. HSS 1150 may be common to GSM core network 1101, GPRS network 1130as well as IP multimedia network 1138.

IP multimedia system 1140 may be built around the call/session controlfunction, of which there are three types: an interrogating CSCF (I-CSCF)1143, a proxy CSCF (P-CSCF) 1142, and a serving CSCF (S-CSCF) 1144. TheP-CSCF 1142 is the MS's first point of contact with the IMS 1140. TheP-CSCF 1142 may forward session initiation protocol (SIP) messagesreceived from the MS to an SIP server in a home network (and vice versa)of the MS. The P-CSCF 1142 may also modify an outgoing request accordingto a set of rules defined by the network operator (for example, addressanalysis and potential modification).

I-CSCF 1143 forms an entrance to a home network and hides the innertopology of the home network from other networks and providesflexibility for selecting an S-CSCF. I-CSCF 1143 may contact subscriberlocation function (SLF) 1145 to determine which HSS 1150 to use for theparticular subscriber, if multiple HSSs 1150 are present. S-CSCF 1144may perform the session control services for MS 1102. This includesrouting originating sessions to external networks and routingterminating sessions to visited networks. S-CSCF 1144 may also decidewhether an application server (AS) 1152 is required to receiveinformation on an incoming SIP session request to ensure appropriateservice handling. This decision may be based on information receivedfrom HSS 1150 (or other sources, such as application server 1152). AS1152 may also communicate to location server 1156 (e.g., a GatewayMobile Location Center (GMLC)) that provides a position (e.g.,latitude/longitude coordinates) of MS 1102.

HSS 1150 may contain a subscriber profile and keep track of which corenetwork node is currently handling the subscriber. It may also supportsubscriber authentication and authorization functions (AAA). In networkswith more than one HSS 1150, a subscriber location function providesinformation on the HSS 1150 that contains the profile of a givensubscriber.

MGCF 1146 may provide interworking functionality between SIP sessioncontrol signaling from the IMS 1140 and ISUP/BICC call control signalingfrom the external GSTN networks (not shown.) It may also control themedia gateway (MGW) 1148 that provides user-plane interworkingfunctionality (e.g., converting between AMR- and PCM-coded voice.) MGW1148 may also communicate with other IP multimedia networks 1154.

Push to Talk over Cellular (PoC) capable mobile telephones may registerwith the wireless network when the telephones are in a predefined area(e.g., job site, etc.) When the mobile telephones leave the area, theymay register with the network in their new location as being outside thepredefined area. This registration, however, does not indicate theactual physical location of the mobile telephones outside thepre-defined area.

FIG. 8 illustrates a PLMN block diagram view of an exemplaryarchitecture in which initiation of a call to an emergency call centermay be incorporated. Mobile Station (MS) 1301 is the physical equipmentused by the PLMN subscriber. In one illustrative embodiment,communications device 40 may serve as Mobile Station 1301. MobileStation 1301 may be one of, but not limited to, a cellular telephone, acellular telephone in combination with another electronic device or anyother wireless mobile communication device.

Mobile Station 1301 may communicate wirelessly with Base Station System(BSS) 1310. BSS 1310 contains a Base Station Controller (BSC) 1311 and aBase Transceiver Station (BTS) 1312. BSS 1310 may include a single BSC1311/BTS 1312 pair (Base Station) or a system of BSC/BTS pairs which arepart of a larger network. BSS 1310 is responsible for communicating withMobile Station 1301 and may support one or more cells. BSS 1310 isresponsible for handling cellular traffic and signaling between MobileStation 1301 and Core Network 1340. Typically, BSS 1310 performsfunctions that include, but are not limited to, digital conversion ofspeech channels, allocation of channels to mobile devices, paging, andtransmission/reception of cellular signals.

Additionally, Mobile Station 1301 may communicate wirelessly with RadioNetwork System (RNS) 1320. RNS 1320 contains a Radio Network Controller(RNC) 1321 and one or more Node(s) B 1322. RNS 1320 may support one ormore cells. RNS 1320 may also include one or more RNC 1321/Node B 1322pairs or alternatively a single RNC 1321 may manage multiple Nodes B1322. RNS 1320 is responsible for communicating with Mobile Station 1301in its geographically defined area. RNC 1321 is responsible forcontrolling the Node(s) B 1322 that are connected to it and is a controlelement in a UMTS radio access network. RNC 1321 performs functions suchas, but not limited to, load control, packet scheduling, handovercontrol, security functions, as well as controlling Mobile Station1301's access to the Core Network (CN) 1340.

The evolved UMTS Terrestrial Radio Access Network (E-UTRAN) 1330 is aradio access network that provides wireless data communications forMobile Station 1301 and User Equipment 1302. E-UTRAN 1330 provideshigher data rates than traditional UMTS. It is part of the Long TermEvolution (LTE) upgrade for mobile networks and later releases meet therequirements of the International Mobile Telecommunications (IMT)Advanced and are commonly known as a 4G networks. E-UTRAN 1330 mayinclude of series of logical network components such as E-UTRAN Node B(eNB) 1331 and E-UTRAN Node B (eNB) 1332. E-UTRAN 1330 may contain oneor more eNBs. User Equipment 1302 may be any user device capable ofconnecting to E-UTRAN 1330 including, but not limited to, a personalcomputer, laptop, mobile device, wireless router, or other devicecapable of wireless connectivity to E-UTRAN 1330. The improvedperformance of the E-UTRAN 1330 relative to a typical UMTS networkallows for increased bandwidth, spectral efficiency, and functionalityincluding, but not limited to, voice, high-speed applications, largedata transfer and IPTV, while still allowing for full mobility.

An exemplary embodiment of a mobile data and communication service thatmay be implemented in the PLMN architecture described in FIG. 8 is theEnhanced Data rates for GSM Evolution (EDGE). EDGE is an enhancement forGPRS networks that implements an improved signal modulation scheme knownas 9-PSK (Phase Shift Keying). By increasing network utilization, EDGEmay achieve up to three times faster data rates as compared to a typicalGPRS network. EDGE may be implemented on any GSM network capable ofhosting a GPRS network, making it an ideal upgrade over GPRS since itmay provide increased functionality of existing network resources.Evolved EDGE networks are becoming standardized in later releases of theradio telecommunication standards, which provide for even greaterefficiency and peak data rates of up to 1 Mbit/s, while still allowingimplementation on existing GPRS-capable network infrastructure.

Typically Mobile Station 1301 may communicate with any or all of BSS1310, RNS 1320, or E-UTRAN 1330. In a illustrative system, each of BSS1310, RNS 1320, and E-UTRAN 1330 may provide Mobile Station 1301 withaccess to Core Network 1340. The Core Network 1340 may include of aseries of devices that route data and communications between end users.Core Network 1340 may provide network service functions to users in theCircuit Switched (CS) domain, the Packet Switched (PS) domain or both.The CS domain refers to connections in which dedicated network resourcesare allocated at the time of connection establishment and then releasedwhen the connection is terminated. The PS domain refers tocommunications and data transfers that make use of autonomous groupingsof bits called packets. Each packet may be routed, manipulated,processed or handled independently of all other packets in the PS domainand does not require dedicated network resources.

The Circuit Switched—Media Gateway Function (CS-MGW) 1341 is part ofCore Network 1340, and interacts with Visitor Location Register (VLR)and Mobile-Services Switching Center (MSC) Server 1360 and Gateway MSCServer 1361 in order to facilitate Core Network 1340 resource control inthe CS domain. Functions of CS-MGW 1341 include, but are not limited to,media conversion, bearer control, payload processing and other mobilenetwork processing such as handover or anchoring. CS-MGW 1340 mayreceive connections to Mobile Station 1301 through BSS 1310, RNS 1320 orboth.

Serving GPRS Support Node (SGSN) 1342 stores subscriber data regardingMobile Station 1301 in order to facilitate network functionality. SGSN1342 may store subscription information such as, but not limited to, theInternational Mobile Subscriber Identity (IMSI), temporary identities,or Packet Data Protocol (PDP) addresses. SGSN 1342 may also storelocation information such as, but not limited to, the Gateway GPRSSupport Node (GGSN) 1344 address for each GGSN where an active PDPexists. GGSN 1344 may implement a location register function to storesubscriber data it receives from SGSN 1342 such as subscription orlocation information.

Serving Gateway (S-GW) 1343 is an interface which provides connectivitybetween E-UTRAN 1330 and Core Network 1340. Functions of S-GW 1343include, but are not limited to, packet routing, packet forwarding,transport level packet processing, event reporting to Policy andCharging Rules Function (PCRF) 1350, and mobility anchoring forinter-network mobility. PCRF 1350 uses information gathered from S-GW1343, as well as other sources, to make applicable policy and chargingdecisions related to data flows, network resources and other networkadministration functions. Packet Data Network Gateway (PDN-GW) 1345 mayprovide user-to-services connectivity functionality including, but notlimited to, network-wide mobility anchoring, bearer session anchoringand control, and IP address allocation for PS domain connections.

Home Subscriber Server (HSS) 1363 is a database for user information,and stores subscription data regarding Mobile Station 1301 or UserEquipment 1302 for handling calls or data sessions. Networks may containone HSS 1363 or more if additional resources are required. Exemplarydata stored by HSS 1363 include, but is not limited to, useridentification, numbering and addressing information, securityinformation, or location information. HSS 1363 may also provide call orsession establishment procedures in both the PS and CS domains.

The VLR/MSC Server 1360 provides user location functionality. WhenMobile Station 1301 enters a new network location, it begins aregistration procedure. A MSC Server for that location transfers thelocation information to the VLR for the area. A VLR and MSC Server maybe located in the same computing environment, as is shown by VLR/MSCServer 1360, or alternatively may be located in separate computingenvironments. A VLR may contain, but is not limited to, user informationsuch as the IMSI, the Temporary Mobile Station Identity (TMSI), theLocal Mobile Station Identity (LMSI), the last known location of themobile station, or the SGSN where the mobile station was previouslyregistered. The MSC server may contain information such as, but notlimited to, procedures for Mobile Station 1301 registration orprocedures for handover of Mobile Station 1301 to a different section ofthe Core Network 1340. GMSC Server 1361 may serve as a connection toalternate GMSC Servers for other mobile stations in larger networks.

Equipment Identity Register (EIR) 1362 is a logical element which maystore the International Mobile Equipment Identities (IMEI) for MobileStation 1301. In a typical embodiment, user equipment may be classifiedas either “white listed” or “black listed” depending on its status inthe network. In one embodiment, if Mobile Station 1301 is stolen and putto use by an unauthorized user, it may be registered as “black listed”in EIR 1362, preventing its use on the network. Mobility ManagementEntity (MME) 1364 is a control node which may track Mobile Station 1301or User Equipment 1302 if the devices are idle. Additional functionalitymay include the ability of MME 1364 to contact an idle Mobile Station1301 or User Equipment 1302 if retransmission of a previous session isrequired.

While example embodiments of systems and methods for intelligentpeer-to-peer management have been described in connection with variouscommunications devices and computing devices/processors, the underlyingconcepts can be applied to any communications or computing device,processor, or system capable of implementing the intelligentpeer-to-peer management systems and methods described. The varioustechniques described herein may be implemented in connection withhardware or software or, where appropriate, with a combination of both.Thus, the methods and apparatuses for intelligent peer-to-peermanagement, or certain aspects or portions thereof, can take the form ofprogram code (i.e., instructions) embodied in tangible and/ornon-transitory media, such as floppy diskettes, CD-ROMs, hard drives, orany other machine-readable storage medium, wherein, when the programcode is loaded into and executed by a machine, such as a computer, themachine becomes an apparatus for intelligent peer-to-peer management. Itis to be understood that a machine-readable storage medium, as describedherein, is not to be construed as a transient signal. In the case ofprogram code execution on programmable computers, the computing devicewill generally include a processor, a storage medium readable by theprocessor (including volatile and non-volatile memory and/or storageelements), at least one input device, and at least one output device.The program(s) can be implemented in assembly or machine language, ifdesired. The language can be a compiled or interpreted language, andcombined with hardware implementations.

Methods and systems for intelligent peer-to-peer management may also bepracticed via communications embodied in the form of program code thatis transmitted over some transmission medium, such as over electricalwiring or cabling, through fiber optics, or via any other form oftransmission, wherein, when the program code is received, loaded into,and executed by a machine, such as an EPROM, a gate array, aprogrammable logic device (PLD), a client computer, or the like, themachine becomes an apparatus for intelligent peer-to-peer management.When implemented on a general-purpose processor, the program codecombines with the processor to provide a unique apparatus that operatesto invoke the functionality of intelligent peer-to-peer management asdescribed herein. Additionally, any storage techniques used inconnection with an intelligent peer-to-peer management system mayinvariably be a combination of hardware and software.

While intelligent peer-to-peer management systems and methods have beendescribed in connection with the various embodiments of the variousfigures, it is to be understood that other similar embodiments may beused or modifications and additions may be made to the describedembodiments for performing the same function of intelligent peer-to-peermanagement without deviating therefrom. For example, one skilled in theart will recognize intelligent peer-to-peer management as described inthe present application may apply to any environment, whether wired orwireless, and may be applied to any number of such devices connected viaa communications network and interacting across the network. Therefore,intelligent peer-to-peer management should not be limited to any singleembodiment, but rather should be construed in breadth and scope inaccordance with the appended claims.

1. A method comprising: intercepting, by a first network device, a firstpeer-to-peer communication that is part of a peer-to-peer communicationsession between a first device capable of peer-to-peer communication anda second device capable of peer-to-peer communication, the peer-to-peercommunication session forwarded to a second network device by the firstnetwork device based on determining the first peer-to-peer communicationcomprises peer-to-peer data; determining, by the second network device,a compatibility of a capability of the peer-to-peer communicationsession; providing, by the second network device, based on thecompatibility, instructions to the first device to adjust a firstcharacteristic of a second peer-to-peer communication to the seconddevice during the peer-to-peer communication session in a manner that iscompatible with the second device; and adjusting by the second networkdevice, a second characteristic of a received portion of a thirdpeer-to-peer communication from the second device in a manner that iscompatible with the first device based on the compatibility.
 2. Themethod of claim 1, further comprising providing instructions to thefirst device to adjust a characteristic of the second peer-to-peercommunication to optimize another application on the second device,based on the compatibility, wherein optimization of the anotherapplication is defined by the second device.
 3. The method of claim 1,wherein the first characteristic of the first peer-to-peer communicationis adjusted in order to perform content adaptation for the seconddevice.
 4. The method of claim 1, further comprising providinginstructions to turn off a capability of the second device based on adefined condition.
 5. The method of claim 4, wherein the definedcondition comprises a location.
 6. The method of claim 1, furthercomprising refraining from inspecting the peer-to-peer communicationsession for a period of time based on the compatibility of thecapability of the peer-to-peer communication session.
 7. The method ofclaim 1, wherein the capability of the first device and the seconddevice comprises processor speed, display screen resolution, oroperating system version.
 8. A network device comprising: a memorystoring instructions; and a a processor coupled to the memory, whereinthe processor executes instructions and performs operations comprising:receiving a first peer-to-peer communication that is part of apeer-to-peer communication session between a first device capable ofpeer-to-peer communication and a second device capable of peer-to-peercommunication; determining a compatibility of a capability of thepeer-to-peer communication session; providing, based on thecompatibility, instructions to the first device to adjust a firstcharacteristic of a second peer-to-peer communication to the seconddevice during the peer-to-peer communication session in a manner that iscompatible with a second device; and adjusting a second characteristicof a received portion of a third peer-to-peer communication from thesecond device in a manner that is compatible with the first device basedon the compatibility.
 9. The network device of claim 8, where theprocessor executing the instructions further performs operationscomprising adjusting the peer-to-peer communication session based on adefined condition.
 10. The network device of claim 8, wherein the firstcharacteristic of the second peer-to-peer communication is adjusted inorder to perform content adaptation for the first device.
 11. Thenetwork device of claim 8, wherein the processor executing theinstructions further performs operations comprising turning off acapability of the first device based on a defined condition.
 12. Thenetwork device of claim 11, wherein the defined condition comprises alocation.
 13. The network device of claim 8, wherein the processorexecuting the instructions further performs operations comprisingsending instructions to refrain from inspecting the peer-to-peercommunication session for a period of time based on the capability ofthe first device.
 14. The network device of claim 8, wherein thecapability of the first device and the second device comprises processorspeed, display screen type, or operating system version.
 15. A systemcomprising: a first mobile device configured to send a firstpeer-to-peer communication; a second mobile device configured to send asecond peer-to-peer communication; a first network device configured toforward the first peer-to-peer communication to a second network deviceafter determining the first peer-to-peer communication comprisespeer-to-peer data; and a second network device configured withinstructions comprising: receiving a first peer-to-peer communicationthat is part of a peer-to-peer communication session between the firstmobile device and the second mobile device; determining a compatibilityof a capability of the peer-to-peer communication session; providing,based on the compatibility, instructions to the first mobile device toadjust a first characteristic of a second peer-to-peer communication tothe second mobile device during the peer-to-peer communication sessionin a manner that is compatible with the second mobile device; andadjusting a second characteristic of a received portion of a thirdpeer-to-peer communication from the second mobile device in a mannerthat is compatible with the first mobile device based on thecompatibility.
 16. The system of claim 15, wherein the second networkdevice is further configured to adjust the second peer-to-peercommunication to optimize another application on the first mobiledevice, based on the compatibility, wherein optimization of the anotherapplication is defined by the first mobile device.
 17. The system ofclaim 15, wherein the second network device is further configured toprovide instructions to turn off a capability of the first mobile devicebased on a defined condition.
 18. The system of claim 17, wherein thedefined condition comprises a location.
 19. The system of claim 15,wherein the capability of the first mobile device and second mobiledevice comprises a processor speed, a display screen type, or anoperating system version.
 20. The system of claim 15, wherein the firstcharacteristic of the second peer-to-peer communication is adjusted inorder to perform content adaptation for the first mobile device.